Expand description
§nanoserde
Data serialization library with zero dependencies. No more syn/proc_macro2/quote in the build tree!
nanoserde also almost do not use any generics, so build size is not going to be bloated with monomorphizated code.
The main difference with “serde” and the reason why “nanoserde” is possible: there is no intermediate data model For each serialisation datatype there is a special macro.
Derive macros available: DeJson, SerJson, DeBin, SerBin, DeRon, SerRon
nanoserde supports some serialization customisation with #[nserde()] attributes.
For #[nserde(..)] supported attributes for each format check Features support matrix
Structs§
- DeBin
Err - The error message when failing to deserialize from raw bytes.
- DeJson
Err - The error message when failing to deserialize a JSON string.
- DeJson
State - The internal state of a JSON deserialization.
- DeRon
Err - The error message when failing to deserialize a RON string.
- DeRon
State - The internal state of a RON deserialization.
- SerJson
State - The internal state of a JSON serialization.
- SerRon
State - The internal state of a RON serialization.
- TomlErr
- The error message when failing to parse a TOML string.
- Toml
Parser - A parser for TOML string values.
Enums§
- DeJson
Tok - A JSON parsed token.
- DeRon
Tok - A RON parsed token.
- Toml
- A TOML value.
- TomlTok
- A TOML parsed token.
Traits§
- DeBin
- A trait for objects that can be deserialized from binary.
- DeJson
- A trait for objects that can be deserialized from JSON.
- DeRon
- A trait for objects that can be deserialized from the RON file format.
- SerBin
- A trait for objects that can be serialized to binary.
- SerJson
- A trait for objects that can be serialized to JSON.
- SerRon
- A trait for objects that can be serialized to the RON file format.